fix(i18n,app-shell): the maker's first sentence promises only what ADR-0112 v1 builds (#8329) - #8439

Closes #8329

What was wrong

The AI build surface's empty state — the first sentence a new user reads on that page, sitting above the start chips — opened with:

Describe an app or workflow in plain language — I draft the objects, screens and automations, then you review and publish.

Workflows and automations are exactly what ADR-0112 v1 refuses (no flows, actions or schedules), so a user who took the sentence at its word was turned down.

This is the last member of a family whose other three were already fixed:

What changed

Two strings, both on the build agent's surface (agentEmptyState() in AiChatPage.tsx):

• console.ai.empty.build.description — "an app or workflow … objects, screens and automations" → "an app … objects, screens and sample data"
• console.ai.empty.editApp.description — "… view or automation" → "… view or dashboard"

The second one is not in the issue body — I found it while tracing the render site. It is the same isBuildAgent() branch (edit mode, ?package=), so it makes the same promise on the same surface.

⚠️ All ten packs, not just en/zh

The issue says "只有 en 与 zh 有这条，其余 8 个语言包走回退". That is not the case — every one of the ten packs shipped its own translated violation (ar/de/es/fr/ja/ko/pt/ru too). A two-language fix would have left eight languages reading the old promise.

The hardcoded defaultValue fallbacks in AiChatPage.tsx are updated alongside, since a stale fallback silently reinstates the sentence for any pack that loses the key.

Deliberately NOT changed

The boundary is v1 AI authoring, not the word "automation". The platform's manual automation paths are real and stay as they are:

Tests

New packages/i18n/src/__tests__/makerEmptyState-v1-scope-8329.test.ts, built on the 7709 suite's shape (54 tests):

1. Every pack defines both descriptions and both titles, non-empty.
2. Neither description in any pack hits that pack's own banned vocabulary — an English-only scan would have declared the five non-Latin packs clean without reading a character of them.
3. Non-vacuity control: each pack's banned list is re-run against the two sentences that pack actually retired, and must flag both.
4. A "didn't revert to its own old string" guard, and positive assertions that the replacement names v1 capabilities.

Verified the guard actually bites: reinstating the old zh string fails 3 tests (expected [ '自动', '流程' ] to deeply equal []).

Verification

• packages/i18n/ — 1090 passed
• packages/app-shell/ — 6261 passed, 1 skipped (649 files)
• @object-ui/i18n type-check clean; app-shell builds clean (tsc passes)
• eslint on changed files: 0 errors
• End-to-end through the real i18n runtime: resolved console.ai.empty.{build,editApp}.description via createI18n({lng}) + changeLanguage() for all ten locales and read back each translated string — not just a read of the pack objects.

⚠️ Not done: a browser screenshot. The card's acceptance asks for one from a running environment; this seat verified through the i18n runtime and the component's unit tests instead. If the screenshot is required to close, it still needs to be taken.

Revert note

When ADR-0112 v2 re-adds flows and actions, both sentences come back — same line of the roadmap as the chips. Recorded in the comment beside the keys in en.ts and in the test's RETIRED map (which holds every pack's original wording).

🤖 Generated with Claude Code